Global Internet Business Solutions ~ GIBS

GIBS IP-Guard Module for Oqtane

Webmaster — Mon, 19 Oct 2026 09:27:00 GMT

Protect Oqtane Sites from 404 Probing with GIBS.Module.IPGuard Public-facing web applications attract constant background noise. Day and night, automated bots scan the internet, probing for exposed admin panels, missing endpoints, common exploits, and stale paths left over from other platforms. Even when those requests fail, they still generate unnecessary server traffic, noisy database logs, and repeated 404 activity. Think of it like a malicious actor walking down a street, rattling every single doorknob to see if one accidentally clicks open. A single 404 error from a normal user might just be a broken link or a typo. But 30 extensionless requests for weird paths in less than a minute? That is a doorknob-rattler looking for a way in. GIBS.Module.IPGuard was built to solve this exact problem in a practical, automated way for the Oqtane ecosystem. Instead of just letting your server endlessly log those misses, IPGuard turns 404 traffic into an active security signal. It watches for repeated failures, counts them by client IP address, and automatically blocks the offenders before they can do any harm. Core Capabilities 1. Automatic IP Blocking & Enforcement The module tracks qualifying 404 requests in real time. When an IP address hits your designated threshold inside the configured time window, it is instantly added to the global block list. Future requests from that IP are cut off immediately at the middleware level, returning an HTTP 403 Forbidden (Access Denied) response before they ever touch your application pipeline. 2. Built for Modern Architecture (X-Forwarded-For Support) Many production Oqtane sites sit safely behind a reverse proxy, load balancer, or Content Delivery Network (like Cloudflare or AWS CloudFront). Standard IP tracking often makes the mistake of logging the proxy's IP instead of the visitor's. IPGuard handles this defensively: it smartly inspects the X-Forwarded-For header first, ensuring you block the actual malicious actor rather than your own upstream infrastructure. 3. Bootstrap 5 Administrator Dashboard Managing your site's security shouldn't require digging through complex database tables. IPGuard features a clean, native administrative UI that is fully Bootstrap 5 ready. It integrates seamlessly with modern Oqtane themes to give you perfect visibility across desktop and mobile devices. Through the control panel, administrators have two core views: Blocked IP Addresses: View the blocked date, total error counts, specific reasons, and automatic country lookups. Recent 404 Attempts: Keep an eye on incoming traffic by reviewing the exact URLs being requested, timestamps, and originating IPs. 4. Manual Overrides & Granular Control Automation is great, but control is better. From the dashboard, you can manually block or unblock IPs, clear out recent logs, or use the "Add To Blocked" shortcut to instantly ban a suspicious IP with a single click. Doing so automatically queries the country data, sets the audit trail to a manual block, and cleanly scrubs that IP's history from your active 404 tracking tables. Best Practice Configurations To help you get started, we recommend the following baseline settings for a balance between tight security and user experience: Setting Recommended Value Purpose 404 Threshold 15–20 attempts High enough to ensure regular users with broken image links won't trigger a false positive, but low enough to swiftly trap a rapid bot scan. Block Window 1–2 Hours A rolling lookback window ensures that slow-probing bots are caught over time without permanently hoarding unnecessary tracking data. Exclude Reserved Routes Enabled Prevents core internal Oqtane routes (like /admin) or standard framework paths (like /_blazor and /_framework) from throwing accidental flags. Built for Real-World Hosting Oqtane environments excel at multi-tenancy, and IPGuard was engineered with that in mind. Settings are optimized at the host level, while blocked records and error attempts are stored globally at the tenant database level rather than fragmenting across individual site instances. Furthermore, the module includes robust runtime safety nets. If tenant persistence isn't fully ready during an installation or a sudden startup gap, IPGuard safely loops past the request pipeline with a warning rather than breaking your live site. Final Thoughts GIBS.Module.IPGuard isn't designed to replace an enterprise-grade upstream Web Application Firewall (WAF). Instead, it provides a highly focused, lightweight, and deeply integrated layer of application defense that slashes log noise and stops automated discovery scripts right in their tracks. If you are running Oqtane in production, it offers the ideal balance of background automation, administrative visibility, and native Bootstrap 5 performance. Ready to secure your Oqtane ecosystem? Download the GIBS IP-Guard Module Contact Our Dev Team

How to check .net runtime version in Azure App Service

Webmaster — Wed, 17 Dec 2025 16:56:00 GMT

Using the Azure Portal Sign in to the Azure portal. Navigate to your App Service and select it. In the left navigation menu, under Settings, select Configuration. Select the General settings tab. In the Stack settings section, you will see the Runtime stack and the specific .NET version being used. Using the Kudu Console (Advanced Tools) The Kudu console provides direct access to the underlying environment and installed runtimes. In the Azure portal, navigate to your App Service. Under Development Tools, select Advanced Tools, then select Go. In the Kudu services window, select Debug console and choose either CMD or PowerShell. Run the appropriate command in the console: For .NET Core and .NET 5+, run dotnet --list-runtimes or dotnet --info to see all installed versions.

Getting AliasId, TenantId and SiteId in Oqtane

Webmaster — Sun, 29 Jun 2025 10:28:00 GMT

private string myaid = ""; protected override async Task OnInitializedAsync() { try { var _aliasid = PageState.Alias.AliasId; var _tenantId = PageState.Alias.TenantId; var _siteId = PageState.Alias.SiteId; myaid = "AliasId: " + _aliasid.ToString() + " TenantId: " + _tenantId.ToString() + " SiteId: " + _siteId.ToString(); } catch (Exception ex) { await logger.LogError(ex, "Error Loading Business Directory Type {Error}", ex.Message); AddModuleMessage(Localizer["Message.LoadError"], MessageType.Error); } }

Here’s how to implement Database calls in Oqtane

Webmaster — Thu, 26 Jun 2025 15:45:00 GMT

1. Add Repository Method Project: Server File: Server\Repository\BusinessCompanyRepository.cs Add this method: public async Task> GetBusinessCompaniesByIsNewItemAsync(int moduleId) { using var db = _factory.CreateDbContext(); return await db.BusinessCompany .Where(c => c.ModuleId == moduleId && c.IsNewItem) .OrderBy(c => c.SortOrder) .AsNoTracking() .ToListAsync(); } 2. Add to Repository Interface Project: Server File: Server\Repository\IBusinessCompanyRepository.cs Add: Task> GetBusinessCompaniesByIsNewItemAsync(int moduleId); 3. Add to Shared Service Interface Project: Shared File: Shared\Interfaces\IBusinessCompanyService.cs Add: Task> GetBusinessCompaniesByIsNewItemAsync(int moduleId); 4. Add to Server Service Implementation Project: Server File: Server\Services\BusinessCompanyService.cs Add: public async Task> GetBusinessCompaniesByIsNewItemAsync(int moduleId) { return await _repository.GetBusinessCompaniesByIsNewItemAsync(moduleId); } 5. Add API Endpoint Project: Server File: Server\Controllers\BusinessCompanyController.cs Add: [HttpGet("isnew/{moduleId}")] public async Task>> GetBusinessCompaniesByIsNewItem(int moduleId) { var companies = await _businessCompanyRepository.GetBusinessCompaniesByIsNewItemAsync(moduleId); return Ok(companies); } 6. Add to Client Service Project: Client File: Client\Services\BusinessCompanyService.cs Add: public async Task> GetBusinessCompaniesByIsNewItemAsync(int moduleId) { return await GetJsonAsync>( CreateAuthorizationPolicyUrl($"{Apiurl}/isnew/{moduleId}", EntityNames.Module, moduleId), Enumerable.Empty().ToList()); } 7. Use in Index.razor Project: Client File: Client\Modules\GIBS.Module.BusinessDirectory\Index.razor a. In your @code block, load the list if no type is selected: private List _newCompanies; protected override async Task OnInitializedAsync() { try { ParentItems = BuildTree(await BusinessDirectoryService.GetBusinessDirectorysAsync(ModuleState.ModuleId)); _BusinessDirectorys = await BusinessDirectoryService.GetBusinessDirectorysAsync(ModuleState.ModuleId); if (PageState.QueryString.ContainsKey("typeId") && int.TryParse(PageState.QueryString["typeId"], out var typeId)) { _selectedTypeId = typeId; _companies = await BusinessCompanyService.GetBusinessCompaniesByTypeAsync(typeId, ModuleState.ModuleId); } else { _selectedTypeId = null; _companies = null; _newCompanies = await BusinessCompanyService.GetBusinessCompaniesByIsNewItemAsync(ModuleState.ModuleId); } } catch (Exception ex) { await logger.LogError(ex, "Error Loading Business Directory Type {Error}", ex.Message); AddModuleMessage(Localizer["Message.LoadError"], MessageType.Error); } } b. In your markup, display the cards when no type is selected: @if (!_selectedTypeId.HasValue) {

@if (_newCompanies == null) {

@Localizer["LoadingCompanies"]

} else if (_newCompanies.Count == 0) {

@Localizer["NoCompaniesFound"]

} else { @foreach (var company in _newCompanies) {

@company.CompanyName

@if (!string.IsNullOrWhiteSpace(company.Address)) {

@company.Address, @company.City, @company.State @company.ZipCode

} @if (!string.IsNullOrWhiteSpace(company.Phone)) {

@company.Phone

} @if (!string.IsNullOrWhiteSpace(company.Website)) {

@company.Website

}

} }

}